🚨 [security] [ruby] Update nokogiri 1.18.9 → 1.19.1 (minor)#97
Open
depfu[bot] wants to merge 1 commit intomainfrom
Open
🚨 [security] [ruby] Update nokogiri 1.18.9 → 1.19.1 (minor)#97depfu[bot] wants to merge 1 commit intomainfrom
depfu[bot] wants to merge 1 commit intomainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
Security Advisories 🚨
🚨 Nokogiri does not check the return value from xmlC14NExecute
Release Notes
1.19.1
1.19.0
1.18.10
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 30 commits:
version bump to v1.19.1doc: update CHANGELOG for upcoming v1.19.1C14n raise on failure (#3600)Raise RuntimeError when canonicalization failsThank sponsors in the READMEdep: update rdoc to v7version bump to v1.19.0dev: convert scripts/test-gem-set to use misedep: Add native Ruby 4 support, drop Ruby 3.1 support (v1.19.x) (#3592)Skip the parser compression test for Windows system libsci: temporarily pin to setup-ruby with windows ruby 4dep: update to minitest 6dep: require JRuby >= 10.0dep: add support for native Ruby 4.0 gemci: bump versions in CI imagesci: avoid bundler collisions in downstream testsci: use arm64 hosts to speed things updep: make sure rdoc is an optional dependencydep(dev): drop explicit Bundler dependencyversion bump to v1.18.10dep: bump vendored libxml2 to v2.13.9 (#3555)ci: work around repeated bundler deadlocksdep: bump vendored libxml2 to v2.13.9[v1.18.x] backport libiconv upgrade to v1.18 (#3550)dep: update vendored libiconv to 1.18Use mirror site to download libiconvci: stop testing Ruby 3.1 windows source buildsci: fix the aarch64 segfault by using a more modern qemuFix errors building Ruby 3.1 on windowsFix errors building Ruby 3.1 on macos 15Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands